home *** CD-ROM | disk | FTP | other *** search
- Path: redstone.interpath.net!usenet
- From: jamie@jamie.interpath.net (Jim Cooper)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Is this a SAS/C bug or have I coded it wrong?
- Date: 14 Jan 1996 18:41:54 GMT
- Organization: Interpath -- Providing Internet access to North Carolina
- Message-ID: <4dbipi$3fd@redstone.interpath.net>
- References: <4cfrc5$gsc@misery.millcomm.com> <4d73u8$lve$2@mhafc.production.compuserve.com>
- NNTP-Posting-Host: raleigh-9.interpath.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- X-NewsReader: Interworks_GRn 3.0b23 December 28, 1995
-
- In article <4d73u8$lve$2@mhafc.production.compuserve.com> Wolf Faust <100116.1070@CompuServe.COM> writes:
- > Try disabling the SAS Peephole optimizer (NOOPTPEEP option). I had
- > several bugs in my code because of the optimizer. I checked the
- > assembler code and after several days it clearly turned out, that
- > when disabling the peephole optimizer the code would be fine...
-
- Please!
-
- If you're going to spread this type of statement, at least state which
- VERSION of SAS/C you were using when you found these problems.
-
- Most current version is 6.56, and several peepholer problems have been
- fixed since 6.50...
-
- --
- Jim Cooper | World: jamie@interpath.com | "I-Net 225 is my life... or at
- | BIX: jcooper | least it seems like it!" :-)
-
- Definition of Perfection: Dysfunctionally Challenged.
-